Skip to main content
Version: older

v3.4.1 to v3.4.2

AUTOMATIC MIGRATION​

  1. Use the BIAToolKit to migrate the project

  2. Manage the conflict (2 solutions)

    1. In BIAToolKit click on "4 - merge Rejected" and search <<<<< in all files.
    • Resolve the conflict manually.
    1. Analyze the .rej file (search "diff a/" in VS code) that have been created in your project folder
    • Apply manually the change.

FRONT​

  1. If some feature use SignalR : Correct the Client for Hub (SignalR) to match with the new model (see plane example). The signalR message are now filter by feature and site.
  2. Add the translation of your roles in i18n files.

BACK​

  1. Replace in the solution using BIA.Net.Core.Application; by using BIA.Net.Core.Domain.Service;

  2. Replace in the solution using BIA.Net.Core.Application.Authentication; by using BIA.Net.Core.Domain.Authentication;

  3. Replace in the solution userRight by userPermission

  4. Replace in the solution UserRight by UserPermission

  5. Correct the table key: Replace tableStateKey = this.useView ? 'xxxxxxxGrid' : undefined; By tableStateKey = this.useView ? 'xxxxxxxGrid' : '';

  6. Correct the Client for Hub (SignalR) to match with the new model (see plane example). The signalR message are now filter by feature and site. The client for hub is now a domain service.

BUILD​

DEPLOY​